This is mind bogling, I have searched everywhere on the web for a solution to this problem, but none of the solutions worked for me.I have a single Exchange 2007 Server and all clients run Outlook 2007.When I test E-mail AutoConfiguration, it returns no errors:Protocol: Exchange RPCServer: CAS Server.domain.comLogin Name: MyNameAvailability Service URL: https://servername.domain.com/ews/exchange.asmxOOF URL: https://servername.domain.com/ews/exchange.asmxOAB URL: https://servername.domain.com/oab/da51c59b-8a03-4fe9-a4e7-8ab74688a178/Unified Message Service URL: https://servername.domain.com/unifiedmessaging/service.asmxAuth Package: UnspecifiedProtocol: Exchange HTTPServer: CAS Server.domain.comLogin Name: MyNameSSL: YesMutual Authentication: YesAvailability Service URL: https://servername.domain.com/ews/exchange.asmxOOF URL: https://servername.domain.com/ews/exchange.asmxOAB URL: https://servername.domain.com/oab/da51c59b-8a03-4fe9-a4e7-8ab74688a178/Unified Message Service URL: https://servername.domain.com/unifiedmessaging/service.asmxAuth Package: BasicCertificate Principal Name: msstd:server.domain.comI also ran Test-OutlookWebServices -Identity: User, returned and error 5008:1003,Information,"About to test AutoDiscover with the e-mail address User."1006,Information,"The Autodiscover service was contacted at https://servername.domain.com/autodiscover/autodiscover.xml."1011,Error,"When querying Availability for User received 5008:"1016,Error,"[EXCH]-Error when contacting the AS service at https://servername.domain.com/ews/exchange.asmx. The elapsed time was 31 milliseconds."1015,Success,"[EXCH]-Successfully contacted the OAB service at https://servername.domain.com/ews/exchange.asmx. The elapsed time was 0 milliseconds."1014,Success,"[EXCH]-Successfully contacted the UM service at https://servername.domain.com/unifiedmessaging/service.asmx. The elapsed time was 0 milliseconds."1011,Error,"When querying Availability for User received 5008:"1016,Error,"[EXPR]-Error when contacting the AS service at https://servername.domain.com/EWS/Exchange.asmx. The elapsed time was 31 milliseconds."1015,Success,"[EXPR]-Successfully contacted the OAB service at https://servername.domain.com/EWS/Exchange.asmx. The elapsed time was 0 milliseconds."1014,Success,"[EXPR]-Successfully contacted the UM service at https://servername.domain.com/UnifiedMessaging/Service.aspx. The elapsed time was 15 milliseconds."1017,Success,"[EXPR]-Successfully contacted the RPC/HTTP service at https://servername.domain.com/Rpc. The elapsed time was 0 milliseconds."1006,Success,"The Autodiscover service was tested successfully."1021,Information,"The following web services generated errors. As in EXCH As in EXPRPlease use the prior output to diagnose and correct the errors." I also ran Test-OutlookWebServices -ClientAccessServer ClientAccessServer01, returned an error 5008:1003,Information,"About to test AutoDiscover with the e-mail address Administrator."1007,Information,"Testing server ESTEQDC01.ESTEQ.com with the published name https://servername.domain.com/ews/exchange.asmx & https://servername.domain.com/EWS/Exchange.asmx."1019,Information,"Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://servername.domain.com/autodiscover/autodiscover.xml."1006,Information,"The Autodiscover service was contacted at https://servername.domain.com/autodiscover/autodiscover.xml."1011,Error,"When querying Availability for Administrator received 5008:"1016,Error,"[EXCH]-Error when contacting the AS service at https://servername.domain.com/ews/exchange.asmx. The elapsed time was 31 milliseconds."1015,Success,"[EXCH]-Successfully contacted the OAB service at https://servername.domain.com/ews/exchange.asmx. The elapsed time was 0 milliseconds."1014,Success,"[EXCH]-Successfully contacted the UM service at https://servername.domain.com/unifiedmessaging/service.asmx. The elapsed time was 15 milliseconds."1011,Error,"When querying Availability for Administrator received 5008:"1016,Error,"[EXPR]-Error when contacting the AS service at https://servername.domain.com/EWS/Exchange.asmx. The elapsed time was 31 milliseconds."1015,Success,"[EXPR]-Successfully contacted the OAB service at https://servername.domain.com/EWS/Exchange.asmx. The elapsed time was 0 milliseconds."1014,Success,"[EXPR]-Successfully contacted the UM service at https://servername.domain.com/UnifiedMessaging/Service.aspx. The elapsed time was 0 milliseconds."1017,Success,"[EXPR]-Successfully contacted the RPC/HTTP service at https://servername.domain.com/Rpc. The elapsed time was 0 milliseconds."1006,Success,"The Autodiscover service was tested successfully."1021,Information,"The following web services generated errors. As in EXCH As in EXPRPlease use the prior output to diagnose and correct the errors."I also checked IIS security settings for EWS, but it is set to Windows IntegratedI can browse to the https://servername.domain.com/ews/exchange.asmx URLFree/Busy works fine in owa, I tired every possible solution, please helpPieter

You check to make sure the SELF account had full access to the mailbox? Can you see FB in the future?Sr. Exchange Engineer - Constellation Energy

Have you tried re-creating the web services virtual directory? 1. Remove-WebServicesVirtualDirectory -identity "Servername\EWS (Default Web Site)" -identity "Servername\EWS (Default Web Site)" 2. IISReset -noforce 3. New-WebServicesVirtualDirectory 4. IISReset -noforceMVP | MCSE:M | MCITP: Enterprise Messaging Administrator | MCTS: OCS + Voice Specialization | http://www.shudnow.net

Thank you Elan,It work, I can't believe it was such a simple fix, thank you so much.Pieter

Dear All, I'm having difficulties with Free/Busy search for my internal users. Internally, using OWA, users are able to do a Free/Busy search but it doesn't work with Outlook 2007. Outside the network, it works well for both (Outlook clients and OWA). I'm using an Exchange Server 2007 Enterprise Edition. My Mailbox Server, HT, UM are on one server (physical box) and the CAS server is on another box ( virtual machine). I'm also using ISA Server 2006 to deploy OWA, Outlook Anywhere, ActiveSync to my remote users. I've been struggling with the Availability Service internally and I thought you might be able to point me to the right direction to fix it. I'm using Split-Brain DNS and a Unified Communications Certificate. It has the CN mail.domainname and the following SANs: owa.domainname, webmail.domainname, mobile.domainname, Autodiscover.domainname, wdcexch.domainname, wdccas.domainname, outlook.domainname, wdcexchange.domainname. Internally, I don’t have a CA set up. The UC cert is installed on the CAS box and I exported it to import it on the ISA Server 2006 in order to publish the different services. Below are the error messages that I'm getting when I run the following commands: [PS] C:\Windows\System32>Get-WebServicesVirtualDirectory |Select Name, *url* |fl Name : EWS (Default Web Site) InternalNLBBypassUrl : https://wdccas.domainname/ews/exchange.asmx InternalUrl : https:// wdccas.domainname /EWS/Exchange.asmx ExternalUrl : https://mail. domainname /EWS/Exchange.asmx [PS] C:\Windows\System32>Get-ClientAccessServer |fl Name : WDCCAS OutlookAnywhereEnabled : True AutoDiscoverServiceCN : wdccas AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service AutoDiscoverServiceInternalUri : https:// wdccas.domainname /Autodiscover/Autodiscover.xml AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596 AutoDiscoverSiteScope : {HQ} IsValid : True OriginatingServer : WDCDC01.domainname ExchangeVersion : 0.1 (8.0.535.0) DistinguishedName : CN=WDCCAS,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=NPCA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domainname,DC=TLD Identity : WDCCAS Guid : 2d247da4-b7a6-4f15-aa7d-a68a1916e63d ObjectCategory : domainname/Configuration/Schema/ms-Exch-Exchange-Server ObjectClass : {top, server, msExchExchangeServer} WhenChanged : 10/2/2009 12:09:19 PM WhenCreated : 10/2/2009 10:13:51 AM [PS] C:\Windows\System32>Test-OutlookWebServices -Identity: username@domainname |fl Id : 1003 Type : Information Message : About to test AutoDiscover with the e-mail address username@domainname. Id : 1006 Type : Information Message : The Autodiscover service was contacted at https:// wdccas.domainname /Autodiscover/Autodiscover.xml. Id : 1013 Type : Error Message : When contacting https:// wdccas.domainname /EWS/Exchange.asmx received the error The request failed with HTTP status 403: Forbidden. Id : 1016 Type : Error Message : [EXCH]-Error when contacting the AS service at https:// wdccas.domainname /EWS/Exchange.asmx. The elapsed time was 718 milliseconds. Id : 1015 Type : Success Message : [EXCH]-Successfully contacted the OAB service at https://wdccas.domainname/EWS/Exchange.asmx. The elapsed time was 0 milliseconds. Id : 1014 Type : Success Message : [EXCH]-Successfully contacted the UM service at https:// wdccas.domainname /UnifiedMessaging/Service.asmx. The elapsed time was 265 milliseconds. Id : 1016 Type : Information Message : [EXPR]-The AS is not configured for this user. Id : 1015 Type : Success Message : [EXPR]-Successfully contacted the OAB service at . The elapsed time was 0 milliseconds. Id : 1014 Type : Information Message : [EXPR]-The UM is not configured for this user. Id : 1017 Type : Success Message : [EXPR]-Successfully contacted the RPC/HTTP service at https://mail.domainname/Rpc. The elapsed time was 15 milliseconds. Id : 1006 Type : Success Message : The Autodiscover service was tested successfully. Id : 1021 Type : Information Message : The following web services generated errors. As in EXCH Please use the prior output to diagnose and correct the errors. I’m getting Event ID: 1013 with HTTP status 403: Forbidden and event ID 1016. And when I run Test-OutlookWebServices, I get the output below: [PS] C:\Windows\System32>Test-OutlookWebServices Id Type Message -- ---- ------- 1003 Information About to test AutoDiscover with the e-mail address username@... 1006 Information The Autodiscover service was contacted at https://wdccas.... 1013 Error When contacting https://wdccas.domainname/EWS/Exchange.asmx rece... 1016 Error [EXCH]-Error when contacting the AS service at https://wdccas.domainname.... 1015 Success [EXCH]-Successfully contacted the OAB service at https://wdccas... 1014 Success [EXCH]-Successfully contacted the UM service at https://wdccas... 1016 Information [EXPR]-The AS is not configured for this user. 1015 Success [EXPR]-Successfully contacted the OAB service at . The elapsed... 1014 Information [EXPR]-The UM is not configured for this user. 1017 Success [EXPR]-Successfully contacted the RPC/HTTP service at https://... 1006 Success The Autodiscover service was tested successfully. 1021 Information The following web services generated errors.... The AS Service is not responding at the URL specified for my internal EWS. I’m don’t know what else to do so any help from this circle of experts will be greatly appreciated. Thank you very much in advance. Armel -

Hi, Came across the same issue after a Service Pack upgrade and one set of users on one MBX were not able to get Free/Busy info from the other set. Increasing the MSExchange Availability event logging level on the CAS servers showed that the CAS servers "could not find a CAS to reach" the problematic MBX server. However, there was no email access issue - MAPI and RPC/HTTPS were working - for the users on the problematic MBX. AD Topology discovery happens very frequently and no problems with email access means that the client Access Server is indeed able to talk to the problematic MBX and that it is only the Free/Busy component that is to be looked into. Free/Busy, Meeting Suggestions, OOF are handled by the Exchange Web Services(EWS) in IIS on the CAS Servers. As Elan has mentioned above, recreating the EWS virtual directory and resetting IIS is a very good solution. To avoid interruptions in IIS, we decided to proceed in the following manner: Since EWS works for users on the non-problematic Second MBX without any issues, there is no configuration problem Since configuration for EWS is correct, we need to look at why EWS has stale data mentioning could not find a way to reach the problematic MBX. The culprit here was IIS Application Pool. By default, the IIS application pool recycles every 29 hours or 1740 minutes. The Application Pool configured for EWS was recycled and Free/Busy info was working again. The same approach has been used for force updating Autodiscover and RPC over HTTPS info, in other instances. Please feel free to correct and clarify if needed. Cheers